refactor(content-blog): decouple getTagsFile from generateBlogPosts by garry00107 · Pull Request #11707 · facebook/docusaurus

garry00107 · 2026-02-01T13:15:21Z

Pre-flight checklist

I have read the Contributing Guidelines on pull requests.
If this is a code change: I have written unit tests and/or added dogfooding pages to fully verify the new behavior.
If this is a new API or substantial change: the PR has an accompanying issue (closes #0000) and the maintainers have approved on my working plan.

Motivation

This PR refactors generateBlogPosts in packages/docusaurus-plugin-content-blog/src/blogUtils.ts to improve the separation of concerns, addressing an existing TODO in the codebase.

Previously, generateBlogPosts was responsible for loading the tags file internally via getTagsFile. This change moves that responsibility to the caller (loadContent in index.ts), making generateBlogPosts a pure function of its inputs with respect to the tags file.

Test Plan

I verified the changes by running the unit tests for the docusaurus-plugin-content-blog package.

Command:

yarn test packages/docusaurus-plugin-content-blog

### Test links

Deploy preview: https://deploy-preview-11707--docusaurus-2.netlify.app/

meta-cla · 2026-02-01T13:15:27Z

Hi @garry00107!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

netlify · 2026-02-01T13:17:30Z

✅ [V2]

Name	Link
🔨 Latest commit	`6420140`
🔍 Latest deploy log	https://app.netlify.com/projects/docusaurus-2/deploys/6985cc106f674f0008b0b021
😎 Deploy Preview	https://deploy-preview-11707--docusaurus-2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

meta-cla · 2026-02-01T13:20:53Z

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

socket-security · 2026-02-06T11:10:40Z

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Package	Supply Chain Security	Quality
@docusaurus/module-type-aliases@3.9.2
@docusaurus/preset-classic@3.9.2
@docusaurus/types@3.9.2
@docusaurus/core@3.9.2
react@16.14.0 ⏵ 19.2.0	⁺¹	⁺⁷
@mdx-js/react@3.1.0 ⏵ 3.1.1
prism-react-renderer@2.4.1
react-dom@16.14.0 ⏵ 19.2.0	⁺¹	⁺³

View full report

socket-security · 2026-02-06T11:10:42Z

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert (click "▶" to expand/collapse)
Warn		Obfuscated code: npm `entities` is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: `?` → `npm/@docusaurus/preset-classic@3.9.2` → `npm/@docusaurus/core@3.9.2` → `npm/entities@4.5.0` ℹ Read more on: This package \| This alert \| What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/entities@4.5.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm `entities` is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: `?` → `npm/@docusaurus/preset-classic@3.9.2` → `npm/@docusaurus/core@3.9.2` → `npm/entities@6.0.1` ℹ Read more on: This package \| This alert \| What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/entities@6.0.1`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm `html-minifier-terser` is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: `?` → `npm/@docusaurus/core@3.9.2` → `npm/html-minifier-terser@7.2.0` ℹ Read more on: This package \| This alert \| What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/html-minifier-terser@7.2.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

refactor(content-blog): decouple getTagsFile from generateBlogPosts

a697f1d

garry00107 requested review from Josh-Cena and slorber as code owners February 1, 2026 13:15

meta-cla bot added the CLA Signed Signed Facebook CLA label Feb 1, 2026

read blog authors/tags in parallel

6420140

slorber added the pr: performance This PR does not add a new behavior, but existing behaviors will be more memory- / time-efficient. label Feb 6, 2026

slorber merged commit 6635ca3 into facebook:main Feb 6, 2026
45 of 46 checks passed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

refactor(content-blog): decouple getTagsFile from generateBlogPosts#11707

refactor(content-blog): decouple getTagsFile from generateBlogPosts#11707
slorber merged 2 commits intofacebook:mainfrom
garry00107:refactor/content-blog-generate-posts

garry00107 commented Feb 1, 2026 •

edited

Loading

Uh oh!

meta-cla bot commented Feb 1, 2026

Uh oh!

netlify bot commented Feb 1, 2026 •

edited

Loading

Uh oh!

meta-cla bot commented Feb 1, 2026

Uh oh!

socket-security bot commented Feb 6, 2026

Uh oh!

socket-security bot commented Feb 6, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

garry00107 commented Feb 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Pre-flight checklist

Motivation

Test Plan

Uh oh!

meta-cla bot commented Feb 1, 2026

Action Required

Process

Uh oh!

netlify bot commented Feb 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ [V2]

Uh oh!

meta-cla bot commented Feb 1, 2026

Uh oh!

socket-security bot commented Feb 6, 2026

Uh oh!

socket-security bot commented Feb 6, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

garry00107 commented Feb 1, 2026 •

edited

Loading

netlify bot commented Feb 1, 2026 •

edited

Loading